An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hi, I've completed all the forms, declarations, store listings and paid the Apple's developer fee in September. On the 1st of October I've submitted my app for a review and got a rejection 2 days later (2.1.0 Performance: App Completeness) asking for login infromation and a video of app's functionality. I've explained that the app has no login and provided the requested video the next day. I have not heard back until the 21st of October with rejection due to Guideline 2.3.2 - Performance - Accurate Metadata, the optional promotional image for an in-app purchase is the same as the app’s icon. I could not update the in-app purchase images, since Apple's reviewer rejected the app and not in-app purchases, so I had to fix in-app purchases and resubmit the app for another review. In addition to the first 5 weeks, the app now has been sitting in review for another week with no idea if the review is even happening... For all I know, I'll check in a month and the app will still be in a review. Apple says 90% of apps are reviewed in 48 hours... Google Play reviewed and approved the app in one week. Does anyone know if the is anything else that can be done or a way to contact Apple directly? I have already requested Expediate review, bu that didn't do anything. Thank you

Hello everyone, Our iOS app version 1.0.0 (build 2026110601) was rejected under Guideline 2.1.0 — App Completeness. The automated message says the app crashed on launch and the review could not proceed. We tested the exact build submitted for review through TestFlight on physical iPhones, iPads, and a Mac, but could not reproduce the crash. We also tested a fresh installation and the app launched normally. The rejection message did not include a crash log, device model, OS version, or reproduction steps. We replied in App Store Connect requesting those details and attached a video showing the app launching successfully, but have not received a response yet. Has anyone encountered a similar situation where a build worked through TestFlight but was reported to crash on launch during App Review? Were you able to obtain the review crash log, or did submitting a new build resolve it? Any advice on what else to check would be appreciated. Thank you.

Hello, Our app Profik Pro (Apple ID 6787445540) was submitted for review on October 10, 2026: version 1.1.14 together with its first four in-app purchase products. The expedited review was confirmed right away ("We'll expedite review for Profik Pro"), and again when I re-requested it on October 15. The submission is still in "Waiting for Review" and has never moved to "In Review". What we have checked: All agreements are Active. We accepted the updated Apple Developer Program License Agreement and Paid Applications Schedule on October 13; banking and tax forms are active too. There are no messages from App Review and nothing marked as action required in App Store Connect. Our other app (Profik, Apple ID 6759965214) was submitted on October 13, reviewed and approved within a day. We also opened a Developer Support case (102995482417) on October 13 and added the details above, but haven't heard back yet. Phone support currently shows as unavailable. Is there anything else we can check on our side, for example something about first-time in-app purchases that could hold a submission? Has anyone seen a submission stay in the expedited queue this long? Thank you!

Hello Apple App Review Team and Developer Community, We are currently unable to release an approved app update due to delays in the In-App Purchase (IAP) review process. We would like to ask if anyone has experienced a similar situation or knows of a possible solution. App Information App ID: 6449141384 App Bundle ID: com.DetailGames.HungryAliens Timeline On November 3, 2026, we submitted a total of 38 items, including IAP products, for review. The submission is still in "Waiting for Review" status, and the review has not yet started. Meanwhile, our latest app build (iOS 1576), submitted on November 6, 2026, has already been approved. Impact of the Review Delay This update includes a limited-time event scheduled to begin on November 9, 2026, and run for approximately four weeks. However, the pending IAP review is preventing us from releasing the approved app build. As a result, we may be unable to deliver the event content to players as scheduled, potentially affecting their opportunity to participate in the event. Questions Has anyone experienced a situation where an app build was approved, but separately submitted IAP products remained in "Waiting for Review" status, preventing the update from being released? If you have successfully resolved a similar issue, we would appreciate hearing what steps you took. If Apple Developer Support does not respond or the issue remains unresolved, is there an official escalation process to request further assistance or review by a higher-level support team? We would greatly appreciate any guidance from an Apple App Review team member or developers who have encountered a similar situation. Thank you for your time and assistance.

Hi there. Our new app has been stuck in "In Review" since October 10. I would've thought that even with being a new developer, which we are, 4 weeks would be more than enough time to review it. Just wondering how we can escalate? Details are: App Name: FyndnSeek Upload Date: Oct 8, 2026 at 8:15 PM Submission ID: 3a0c2690-4039-42f5-965b-d5ccf694a999

Our first submission has now been rejected under Guideline 2.1(b), with the message: "the in-app purchases do not load successfully." Each review was performed on an iPad Air 11-inch (M3) running iPadOS 26.6. The app sells only auto-renewable subscriptions. We cannot reproduce the failure, and we have verified every part of the configuration we can think of. WHAT WE VERIFIED (via the App Store Connect API, not just the UI) Two subscriptions in one group, state READY_TO_SUBMIT Product IDs exactly match what the app requests Available in 175 territories, including the United States Prices set, en-US localizations present for both products and for the group App review screenshots attached to both, state COMPLETE Both subscriptions are included in the review submission (READY_FOR_REVIEW) Paid Apps Agreement: Active. Bank account: Active. Tax forms: Active. WHAT WORKS On our own devices, installed via TestFlight (sandbox environment), the products load correctly and a purchase completes and activates as expected. This works on both a real Apple ID and a Sandbox Tester account. WHAT WE OBSERVED FROM THE REVIEW SESSION We use RevenueCat. Their server-side API returns our offering with both packages and the correct product identifiers, so the offering metadata is fine. Our backend also shows that the reviewer's session reached our servers and signed in successfully at the review timestamp, so the device had working network connectivity. That leaves StoreKit itself returning no products on the reviewer's device, which is what empties the offering. QUESTIONS Are there known conditions under which StoreKit returns no products in the App Review sandbox for subscriptions that are in "Ready to Submit" and are attached to the same submission as the binary? For an app that has never been approved, is product loading during review handled differently from a normal sandbox session on a released app? Is there any way to obtain diagnostics from a review session, or to ask the reviewer for a screenshot of the failing screen? Replies in Resolution Center so far have only repeated the original rejection text. Is there anything specific to iPadOS 26.6 that could affect StoreKit 2 product lookups? For the next submission we have added a timeout and automatic retries around the product lookup, plus a visible retry control instead of a spinner, in case the failure is a transient cold-start timeout. But we would rather understand the actual cause than keep guessing. Any pointers appreciated.

Hi, Our first app release has been in Waiting for Review since November 1, 2026 and has not moved to In Review yet. App: Calena Apple ID: 6809952850 Version: 1.2.12 (31) Submission ID: 8d78f093-4707-4e93-bcc7-0c5bcff3ecd2 Submitted: November 1, 2026, 12:31 UTC What we checked so far: There are no messages from App Review in App Store Connect and no emails The build is processed and valid We submitted an expedited review request We opened a ticket with Developer Support on November 3, 2026 (case ID 103017786436), no response yet We are not new to the App Store. Our other app on the same developer account, Calena Driver (Apple ID 6806524950), is live and actively maintained. Its updates have been reviewed and approved quickly every time, versions 2.0.1, 2.2.0 and 2.2.12 since August. Version 2.2.12 was submitted on the same day as this submission, 5 minutes later, and it was approved without any delay. Only the customer app has been waiting. The two apps work together, so drivers are waiting for bookings and customers cannot book until the customer app is released. We do not want to cancel and resubmit because that would put us back at the end of the queue. Could someone from App Review please check whether anything is blocking this submission? Thank you.

An optional coaching feature in my planned app would, after explicit opt-in, send a short text summary (for example sleep duration or heart rate variability over the last week) to a third-party AI service to generate advice for that same user. The data is not used for advertising, marketing or data mining. Guideline 5.1.3(i) allows disclosure of HealthKit-derived data only "for improving health management, or for the purpose of health research, and then only with permission", and DPLA 3.3.3(H) allows disclosure to a third party only with prior express consent and only to provide health, motion or fitness services. Is a per-user coaching feature like this within what 5.1.3(i) and 3.3.3(H) permit? Does it matter whether the summarised values were entered manually (and stored in HealthKit) or measured by a device? I understand this is not a pre-approval; I would like to know how the rule is meant to be read. Thank you.

I am planning an iOS app for strength training, nutrition and sleep. Before I build the data layer I would like to understand how Apple reads the following rules. Planned design: Body measurements and sleep values live in HealthKit only and are never written to iCloud or CloudKit. Training sessions and meal entries (food, calories, macronutrients, entered manually or by barcode scan) are stored on the device and in the user's private CloudKit database. Nothing is stored on our own servers. The app also caches packaged food products the user has scanned (name, ingredients, allergens, nutrition facts from the public Open Food Facts database) in the same private CloudKit database. Guideline 5.1.3(ii) says apps "may not store personal health information in iCloud", and DPLA 3.3.3(D) restricts using iCloud or CloudKit for "sensitive, individually-identifiable health information" unless Apple permits it in writing. Questions: Does a meal log or a product cache in the user's private CloudKit database count as "personal health information" in this sense, as long as no HealthKit values are stored there? Is the answer different if the private CloudKit data is end-to-end encrypted (encryptedValues)? I understand that App Review cannot pre-approve an app. I am only asking how the rule is meant to be read. Thank you.

Hi everyone, My app was rejected under Guideline 4.3 – Design: Spam, and I'd appreciate some advice on how to get it approved and released. The idea came from playing in a football team. I thought it would be nice if the team members and the coach could give each other points and feedback, so we could see who the MVP was and get a bit more motivated to play better. I built this app myself; it's not based on a template or a white-label service. I looked for similar apps on the App Store and couldn't find anything like it, so I don't understand why it was flagged as spam. I've already submitted an appeal to the App Review Board and also replied again to the rejection message, but I haven't heard back yet. A few questions: How long does the appeal usually take? While I wait, can I make some changes and submit a new build for review, or could that cause problems with the appeal? Any help would be really appreciated. Thanks!

Apple's Changes User-Generated Content rule changes in Apple News 16/Oct//2026 1.2: Content moderation requirements now explicitly cover nonconsensual intimate imagery — including imagery generated using AI tools — as content that apps must proactively prevent and remove from their platforms proactively prevent sounds like we are expected to check for nudity in image uploads? Checking the actual review guideline seems to confirm this expectation Apps that enable users to create, generate, upload, share, or otherwise contribute content ... To prevent abuse, such apps must include: A method for filtering objectionable material from being posted to the app My context for concern I have an app which allows people to create rich content for iMessage. I want to give people the ability to resell templates through an in-app store (eg: interactive greeting cards). Those templates will be visible to all users who wish to use them, free or paid. It seems that anything that will allow creators to post such shared content for reuse now needs content checkers. Trivial picture uploads need review?? One comment on Reddit expressed another developer's concern - does this even extend to profile pictures on a shared directory?

I’d like to raise how our app’s review has gone, in the hope that someone at App Review sees it, and to ask whether other developers are seeing the same thing. Our app is Suan, a sleep audio app. It’s iPhone-only. It has no server and no account, and one auto-renewing yearly subscription shown with Apple’s own SubscriptionStoreView. What has happened: 30 Oct: submitted. 3 Nov: rejected under 5.1.1(iv) for the wording on our Apple Health screen. Fair enough. Fixed and resubmitted the same day. 5 Nov: rejected on three points: 5.1.1(iv) again, for a button label that was already there in the first review and wasn’t mentioned then; 2.1(b): the reviewer couldn’t find the In-App Purchase; 2.1(a): every audio download failed on an iPad Air (M3) on iPadOS 27. We fixed all three. Every track now ships inside the app, so nothing downloads at all. The review notes say step by step where the subscription is: it appears straight after onboarding, it’s the first section in Settings, and it opens when you tap play on any track. 8 Nov: rejected under 2.1(a) for “an error during onboarding”, again on the iPad Air (M3). The reviewer’s screenshot shows Apple’s SubscriptionStoreView reporting “NSURLErrorDomain error -1009”. That error means the device is not connected to the internet. The screen is Apple’s own, loading our subscription from the App Store sandbox. Our onboarding makes no network requests. So of the issues raised, two came from the review device having no connection, one was a subscription that the review notes explain how to find, and one was a button that passed the first review. None of them happen on our own iPhones. We’ve replied to every rejection in App Store Connect, and resubmitted each time within hours. The Android version of the same app, with the same features, content and subscription, went through Google Play’s review and was approved. Each round costs us two to three days, and we’ve now spent about two weeks on a launch that was ready at the start. I’d be grateful for a few things: When the error in a screenshot is a network error like -1009, could reviewers check the device’s connection, or try again, before rejecting? Could every issue be raised in one review, rather than a new one appearing after each fix? Could reviewers read the review notes? For us they answered the question the rejection asked. Has anyone else had StoreKit or network failures in review on iPad Air (M3) with iPadOS 27? I’ve seen a few threads describing the same thing. If anyone found a way past it, I’d love to hear it. The quality of the testing effort has been pretty poor. Thank you.

Hi everyone, I recently submitted my iOS application for App Store review, but it has been showing “Waiting for Review” for some time now. Here are my submission details: ● App Name: Eazydezk ● Version: 1.0 ● Build: 10 ● Submission Date: November 5, 2026 ● Current Status: Waiting for ReviewI wanted to check whether other developers are experiencing similar delays with App Store submissions recently. I understand that review times can vary depending on the application and submission queue. However, I would appreciate hearing about recent review timelines from developers who have submitted apps this week. A few questions: ● How long did your latest app submission take to move from “Waiting for Review” to “In Review”? ● Are first-time app submissions taking longer than usual? ● Is there currently any delay in the App Review process?I’m not looking to expedite the review unnecessarily, just trying to understand whether this is a general delay or something specific to my submission. Would appreciate hearing about your recent experiences. Thanks!

@AppReview One of our live apps was flagged following a re-evaluation. We had not submitted any update. The message we received: Guideline 4.3 - Design - Spam We noticed the app provides the same feature set and experience as other apps already available from you and associated developer account(s) on the App Store. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. We were asked to submit a compliant update by November 21, 2026, otherwise the app will be removed from sale. We have reviewed all apps under our developer account and could not identify any app with the same core functionality. We have already replied in App Store Connect with a detailed explanation and a screen recording of the app, and we are currently awaiting a response. As the November 21, 2026 deadline is approaching, we kindly ask that our explanation and screen recording be reviewed before the removal date. Could you also please let us know which apps were identified as similar, so we can address the issue in time? Thank you.

Hi, My app's first version has been in "Waiting for Review" since October 28, 2026, 12:11 PM. App: Helium – Squeaky Voice Changer Apple ID: 6825700812 Submission ID: a49a4eaa-acd9-4c90-ba74-2efd935a8c15 Build: 1.0 (4) App Review sent feedback on October 23 and October 27. I addressed every point (App Tracking Transparency implementation, third-party AI clarification, face data questions), replied in App Store Connect and resubmitted on October 28. I also submitted an expedited review request. The message thread is now locked, so today I updated the App Review Information notes to confirm that build 4 is the build under review and to explain where the ATT prompt appears. Could someone from App Review check whether anything else is needed from my side? Thank you.

Hello, I know this forum is not meant for account or enrollment issues, and I apologize for posting here. But I honestly have no other option left. Apple Developer Support has been extremely slow to respond, and since I am in Pakistan, the phone call-back option is not even available in my region. I feel completely stuck, with no way to talk to anyone at Apple about my own account. OLD ISSUE (Case ID: 103006700501) I enrolled in the Apple Developer Program as an Individual using the Apple Developer app on my iPhone. My enrollment got stuck with "Contact Us to Continue" and "ID Verification Rejected". I submitted the support form multiple times and never received a single reply. After waiting about 7 days, the Enroll option was suddenly re-enabled on my account. But no one replied to my case, no one explained what went wrong, and no one told me what I needed to fix. The button just came back silently. NEW ISSUE (Case ID: 103012960482) As soon as the Enroll option was re-enabled, I applied again. I used the same passport, the same legal name (exactly as it appears on my passport), the same residential address, and the same details as before. All of my information is correct and genuine. I have nothing to hide. Within about an hour, my enrollment was rejected again. The app now shows "ID Verification Rejected" and "Contact Us to Continue" once more. I have submitted yet another support request under Membership and Account > Program Enrollment. I have to be honest: this has been one of the most frustrating experiences I have had. I waited 7 long days for my account to be re-enabled, only for it to be rejected again within an hour, with no reason at all. I am a genuine person using my real passport, and I am being treated as if I have done something wrong, without anyone telling me what it is. Every day this drags on, my business loses time. My customers are waiting for our iOS app, and I keep telling them "soon" without knowing when, or even if, this will ever be resolved. I cannot fix a problem that no one will explain to me. If I simply re-apply with the same genuine documents, I will get the same result again. I do not want to keep going around in this loop of waiting a week, applying, getting rejected within an hour, and hearing nothing back. MY REQUEST Please do not just re-enable the Enroll button again without any explanation. Instead, could an Apple staff member or the enrollment verification team please do one of the following: Tell me what exactly is causing the rejection, so I can fix it. Ask me to send my documents directly for manual verification. I am ready to provide my passport, national ID card (CNIC), proof of address, business registration documents, or anything else you need, right away. Review my case and approve my application. About me: I am the founder of a licensed travel agency in Pakistan, and I want to publish our iOS app on the App Store so our customers can book flights and Umrah packages from their iPhones. Case IDs: Previous: 103006700501 Current: 103012960482 I am hoping Quinn "The Eskimo!" or any other Apple staff member can please look into my account or escalate it to the enrollment team. I am not asking for any special treatment, just a clear answer and a fair chance to get verified. Any help would be truly appreciated. Thank you, Ahsan Raza

I don’t understand why Apple doesn’t allocate more staff to App Review if the current team cannot keep up with submissions. These delays take a toll on developers, both financially and mentally. Many of us are independent developers or small teams, not large companies with the resources to absorb long periods of uncertainty. We pay $99 a year for the Developer Program, yet our membership time keeps running while we wait for review. What if, after spending months developing an app and dealing with review delays, a developer has less than two weeks left before renewal by the time their app finally goes live? Having to pay another $99 so soon after launch feels unfair. I understand that Apple needs to protect users and maintain quality standards. But surely there is a way to do that while also providing more predictable review times and clearer communication. Could Apple increase review staffing, provide more useful queue updates, or consider membership extensions for unusually long review delays? Small developers put significant time, money, and effort into building their apps. We’re asking for a process that respects that investment. 🙏

I have submited my app for review Oct 22, 2026 at 12:42 PM after 4 days Oct 26, 2026 at 5:25 PM app got rejected, requested motre infomration and screenrecording , i have submited everything and resubmited back Oct 26, 2026 at 9:15 PM status nevere changed form WIATING TO REVIEW, on Oct 31, 2026 at 4:11 PM I canceled submition created new BUILD and resubmit app on Oct 31, 2026 at 4:25 PM Nov 2, 2026 at 2:06 PM rejected the app again and resubmitted updated build on Nov 2, 2026 at 2:12 PM statsu nevere change, what is going on with APPLE? I have created 3 ticked regarding this issue. no answer, no contact back, nothing ... I NEED SOMEONE FORM APPLE TO EXPLAIN WHAT IS GOING ON AND RESOLVE THE ISSUE I've seen in my admin portal that apple created an account and never tested the game. seems like they don't wanna work at all. 2 accounts has been created and app never been tested. my Admin consol can truck the players current page in the game. like main menu, or in the room. once account created then app was closed. no crushes, no bugs, they just didn't test it, and my app is still showing Waiting for Review. I can't undertand what they doing. They don't care at all, they forget that it is B2B relation and they must be professional.

Hello, I resubmitted my app, PlayJar, version 1.0.10, together with its “No Ads Monthly” subscription on 1 November. As of 8 November, both still show “Waiting for Review” in App Store Connect. We had hoped to launch the app before Diwali, but it is still waiting for review. I’ve also requested an expedited review and contacted Apple for help, but the review status remains unchanged. Is anyone else experiencing a similar delay? Is there anything else I should check, or another way to follow up without withdrawing the submission? I’ve attached screenshots showing the review statuses and submission date. Thank you.

Hi everyone, I already posted here on September 26. Six weeks later, our app X-Friend (Apple ID 6780055622), which is ready for public release, is still not live. In those six weeks it was reviewed only twice. Both times it was rejected with the same copy-and-paste sentence (Guideline 1.1.4). There was no specific reason, no screenshot and no indication of what the reviewer saw. Just "somewhere in your app or metadata". We called App Review support. The person on the phone could not see any information about our review, could not do anything and told us to wait. What is support for if it can't see anything? We have been trying to get into the App Store since August. Every cycle means waiting, sometimes more than four weeks, only to receive the same sentence again. Meanwhile we have changed almost everything: demo account, store and subscription texts, age rating, website, screenshots, reviewer notes. We are guessing, because nobody tells us where the problem is. The same app is live on Google Play for months now. Reviews there come back within about three days, and when something is wrong they attach a screenshot and tell us exactly what and where. How can an app be rejected repeatedly for the same guideline without anyone pointing to the actual issue? "Somewhere in the app OR the metadata" is not actionable. We want to comply. All we ask for: The specific screen, content or metadata field, ideally with a screenshot. All findings in one pass. A support contact who can actually see our case. If anyone from App Review reads this, please look at Apple ID 6780055622 and tell us concretely what needs to change. And if other developers have been through this: how did you get out of this loop? Thanks.